projects / ostree.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: f1da7ec) | patch
libostree: Ensure progress keys are all always set
authorPhilip Withnall <withnall@endlessm.com>
Fri, 5 May 2017 14:17:13 +0000 (15:17 +0100)
committerAtomic Bot <atomic-devel@projectatomic.io>
Fri, 5 May 2017 14:58:03 +0000 (14:58 +0000)
commitbf9772f2316a567566c20979e5247b2928287253
tree00ab8bfad65de70283c1a7c5069f9174e4b63de2tree | snapshot
parentf1da7ec300d2827460d138a0f316ad6b77501336commit | diff
libostree: Ensure progress keys are all always set

If one of the progress keys is set in a pull operation, a ::changed
signal is emitted on the progress object, and the callback for that
could query any of the progress keys — so they all need to be set,
otherwise we get an assertion failure in ostree_async_progress_get() due
to a named key not existing.

Spotted by Dan Nicholson in PR #819.

Signed-off-by: Philip Withnall <withnall@endlessm.com>
Closes: #835
Approved by: cgwalters
src/libostree/ostree-repo-pull.c diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.